Skip to content

Add threaded conversation view to Burner - Messages#923

Merged
abrignoni merged 1 commit into
mainfrom
burner-messages-chat-view
Jul 3, 2026
Merged

Add threaded conversation view to Burner - Messages#923
abrignoni merged 1 commit into
mainfrom
burner-messages-chat-view

Conversation

@abrignoni

Copy link
Copy Markdown
Owner

Summary

ALEAPP's Burner - Messages (burnerMessages.py, by Heather Charpentier) was the one Burner chat artifact across the LEAPPs without a threaded chat view — both iLEAPP Burner message artifacts (burner.py, burnerCache.py) already have one. This adds the LAVA conversation data_view using only the existing columns; parsing and schema are untouched (13-line metadata-only diff).

Mapping

  • Threads keyed and labeled by Contact (per-number conversations)
  • directionSentValue: "Outgoing" (matches the query's CASE output)
  • Received bubbles labeled with the contact number; sent bubbles use sentMessageStaticLabel: "Local User" — verified against LAVA's queryConversation (platform.electron.js:89-96), which substitutes the static label for sent-direction rows, so outgoing messages are never mislabeled with the contact's number
  • timeColumn: Timestamp (datetime-typed)

Also bumped last_update_date.

Testing

  • pylint --disable=C,R10.00/10
  • All view column refs validated against data_headers (no dangling names)
  • PluginLoader registers the artifact with data_views intact
  • ALEAPP lavafuncs normalizes the view and sanitizes column names (lava_process_artifact); string directionSentValue is quoted by LAVA at query time

Wire the LAVA conversation data_view onto the existing columns: threads
keyed and labeled by Contact, direction 'Outgoing' as sent, received
bubbles labeled with the contact number and sent bubbles with the static
'Local User' label (sentMessageStaticLabel). No schema or parsing changes.
@abrignoni abrignoni merged commit 358db94 into main Jul 3, 2026
2 checks passed
@abrignoni abrignoni deleted the burner-messages-chat-view branch July 3, 2026 01:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant